<ui:composition xmlns="http://www.w3.org/1999/xhtml"
	xmlns:h="http://java.sun.com/jsf/html"
	xmlns:f="http://java.sun.com/jsf/core"
	xmlns:ui="http://java.sun.com/jsf/facelets"
	template="adminTemplate.xhtml">


	<ui:define name="pageIntro">
		<h2>Create an Action</h2>
		<p class="lftText">Use this form to create an <span>action</span>.<br />
		Actions are step in a life of an <span>issue</span>. Let's assume that
		you use weebill to track bugs of a software project. You should have
		steps such "Open","Under Development","Resolved","Closed" or
		"Re-opened". Each of these steps are called <span>"Action"</span>'s. <br />
		Group of actions are called <span>"ActionPath"</span>'s. So in fact a
		bug tracking is an ActionPath. Another example for ActionPath can be a
		"Feature Request".<br />
		You can add listeners to start and end of actions and customize
		navigation. This page is used only to create an action.<br />
		You can add listeners while editing the ActionPath's.<br />
		Action's are performed by users. So you should also select the roles
		that can perform this kind of action. But an action for example "Open"
		can be used in more then one ActionPath's such in a big and feature
		request. For this reason, roles are assigned while editing the
		ActionPath like listeners.</p>
	</ui:define>


	<ui:define name="mainForm">
		<h:form id="crtActForm">
			<h:panelGrid columns="2">

				<h:outputLabel for="crtActName" value="Name"></h:outputLabel>
				<h:inputText id="crtActName" value="#{createAction.action.name}"></h:inputText>

				<h:outputLabel for="crtActDescription" value="Description"></h:outputLabel>
				<h:inputText id="crtActDescription"
					value="#{createAction.action.description}"></h:inputText>

			</h:panelGrid>
			<h:commandButton id="crtActSbt" value="Save"
				action="#{createAction.save}"></h:commandButton>
		</h:form>
	</ui:define>
</ui:composition>
